Repository navigation
ci(dev-close-notice): refresh 2026 dev-close windows through 2.29 - #13858
Merged
Merged
Conversation
Update DEV_CLOSE_PERIODS to match the release plan (issue #10568): 2.25 through 2.29. The previous single 2.24 entry was stale, so the notice workflow was inactive during the current 2.25 dev close. Also gitignore local Claude/Playwright artifacts.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Updates
DEV_CLOSE_PERIODSinpr-dev-close-notice.yamlto match the release plan — versions 2.25 through 2.29.Why
The array previously held only a single stale 2.24 entry (window ended 2026-07-09). As a result the notice workflow was inactive during the current 2.25 dev close (2026-07-22 → 2026-07-29). Verified locally that today resolves to the 2.25 window with the new entries.
Also adds a
.gitignoreentry for local Claude/Playwright artifacts.